Aztec Technical Specifications

These paths and subdirs will need to have read / write permissions set for the user running the Aztec Management System session.

The following paths (and subdirs) require write permissions: The Aztec Management System, ZBS Dimensions and ZCPS+ATS will have the c:\program files\ (x86) location if installed under 64-bit operating system

Appropriate x86 paths required if 64-bit.

Aztec Management System

• c:\temp

• c:\program files\zonal

• c:\program files\common files\system\ole db\data links

• <data location>path HKEY_LOCAL_MACHINE\SOFTWARE\ZONAL\Aztec\DataLocation

Electronic Funds Transfer (EFT)

• c:\prizm\+subdirs

• c:\program files\Borland\common files\bde

• c:\windows\ackltd.ini

• c:\program files\Zonal

• c:\program files\BDE

• c:\program files\Borland

Zonal Business Systems (ZBS) Dimensions

• c:\program files\zbs

Automated Purchase Order System (APOS)

• c:\zonal

Zonal Card Payment System (ZCPS)

• c:\program files\zonal

• c:\program files\DataCash\ATS

• c:\Documents and Settings\All Users\Applications Data\Datacash\ATS (Windows xp)

• c:\programdata\DataCash\ATS (Windows 7)

POS Integration Engine (formerly known as iZone)

• c:\program files\zonal

• %PROGRAMDATA%\ZonalCLM

Zonal Connect Framework (ZCF)

• c:\program files\zonal

• %PROGRAMDATA%\Zonal\DataAccessApi

• %PROGRAMDATA%\Zonal\CommunicationFramework\SiteProxy

Fourth Hospitality (Imports)

• c:\programdata\zonal\aztec\productimportfiles

Application	Service Name	Display Name	Install Type
APOS	SvCorpControl	APOS Controller	[H] [S]
APOS	Ajaservice	ATP Server	[H] [S]
Aztec Distribution	AztecDistributionSiteService	Aztec Distribution Service	[S]
Aztec Import Service	AztecImportService	Aztec Import Service	[H]
Aztec Management System	AztecCommsJoblinkService	Aztec Comms Service	[C] [H] [S]
Aztec Management System	AztecController	Aztec Controller	[C] [H] [S]
Aztec Management System	EPoSManager	Aztec EPoS Manager	[M] [S]
Aztec Management System	AztecServiceWatchdog	Aztec Service Watchdog	[A]
Aztec Management System	AztecSpotCheck	Aztec Spot Check	[M] [S]
Aztec Management System	AztecApache	Aztec Apache Service	[M] [S]
Aztec Management System	AztecBohService	Aztec BoH Service	[A]
Aztec Tables Management Service (Tables)	AztecTableMgmtService	Aztec Table Management Service	[M] [S]
Microsoft SQL Server	MSSQLSERVER	SQL Server (MSSQLSERVER)	[A]
Microsoft SQL Server	SQLSERVERAGENT	SQL Server Agent (MSSQLSERVER)	[A]
POS Integration Engine (formerly iZone)	Zonal CLM Engine	Zonal CLM Engine	[M] [S]
POS Integration Engine (formerly iZone)	PSAgent	Zonal CLM	[M] [S]
ZCPS + ATS	ATS	Datacash ATS	[S]
ZCPS +ATS	ACKNODESVC	DataCash ATS Node Encryption Service	[S]
ZCPS +ATS	EoDSvc	DataCash ATS Scheduled EOD Service	[S]
ZCPS +ATS	ZcpsService	Zonal Card Payment System	[S]
Zonal Connect	AztecMOAService	Aztec MOA Service	[M] [S]
Zonal Data Transformation Service (ZDTS)	ZdtsSvc	Zonal DTS Service	[H]
ZonalEFT	ZonalEFT	Zonal EFT	[A]
ZonalEFT	ACKNodeSvc	ACK EFT Node Encryption Service	[A]
ZonalEFT	ACKEstateSvc	ACK EFTEstate Encryption Service	[H]

 

Install Types:
[A] - All
[C] - Comms Server Only
[H] - Head Office Only
[M] - Site Master
[S] - Site Only

All of these services will be installed to run under ‘local system’ by default

All of the listed services can be run under service accounts, but should have file permissions set as detailed in the paths sub section; and with ‘interact with desktop’ configured

 

Electronic Funds Transfer (EFT)

• A minimal user account called ACKNodeUser is also created upon install of ACK EFT, which the ACKNodeSvc service is already run under

Automated Purchase Order System (APOS)

• In the case of Head Office APOS services being configured to run under a service user, access must be granted to shares (configured in the HKEY_LOCAL_MACHINE\Software\Zonal\AJA registry key on each machine used to transfer AZTEC APOS2 B2B files). The service user(s) will need both read and write permissions on the share(s)

Zonal Card Payment System (ZCPS) + ATS

• A minimal user account called ACKNodeUser is also created upon install of ACK EFT, which the ACKNodeSvc service is already run under

SQL Server

• Sites running Conqueur Interface: SQL server agent service requires access to common shares to import / export Conqueror csv files. The paths for the shares are defined in the ini files, and the service user must carry read and write permissions to those paths

Aztec Management System

• Aztec 3.7.2 introduced a change to Internal Transfers in Aztec Purchasing which now means the Windows Distributed Transaction coordinator service is required to be running in order to complete the transfer. It needs to be running on both the sending and receiving sites

Aztec Distribution

• User Execution Credentials will only be required where Local System is unable to execute the distribution manifest. To use ‘User Execution Credentials’ the following local security policies will require the executing user to be added:

  • Local Security settings\Local Policies\User Rights Assignment\logon as a batch

  • Local Security settings\Local Policies\User Rights Assignment\replace a process level token

Aztec Comms Integration

• Users running the AztecCommsJoblink service will require the 'Logon as a Service' right added

• This service interacts with other Comms Services (if applicable) via .NET remoting. Having more than one comms server requires a centrally accessible folder, into which incoming/outgoing files are passed. This is only for unmanaged code plugins for example: APOS, Kitchen Screens etc This share location is configured from inside the Aztec Shell and can be validated using the ‘Test Environment’ button whilst the root node is selected in the comms estate structure tree view. Where share permissions are desirable, both read and write access is required for this share for the AztecCommsJoblink service user(s) if applicable

 

Aztec installs will deploy a windows scheduled task to zip and maintain application logs – this runs daily and results in archive zips – this is dropped and recreated by every install.

Name	Run-as	Information
Aztec Log File Archiver	NT AUTHORITY\SYSTEM	Zips Aztec log files every day. Runs in..\Aztec folder

 

All users are expected to have read access throughout common areas in the registry as default, unless read access is explicitly denied.

The below registry keys will need to have Full Control permissions: The Aztec Management System, ZBS Aztec Dimensions and ZCPS +ATS will use Wow6432Node key if installed under an x64 bit environment

Aztec Management System

• hkey_local_machine\software\Zonal\ + subkeys

• hkey_local_machine\software\Zonal Retail Data Systems\ + subkeys

• hkey_local_machine\software\Zonal Retail Data Systems Ltd\ + subkeys

• hkey_local_user\control panel\International\+subkeys

Electronic Funds Transfer (EFT)

• hkey_current_user\software\borland\ + subkeys

• hkey_local_machine\software\borland\ + subkeys

Zonal Business Systems (ZBS) Dimensions

• <Uses the same keys as the Aztec Management System>

Automated Purchase Order System (APOS)

• hkey_local_machine\software\Aja

Zonal Card Payment System (ZCPS) + ATS

• hkey_local_machine\software\Zonal\ZCPS

• hkey_local_machine\software\Zonal\ZCPS\Plugins\ATS

POS Integration Engine (formerly iZone)

• <Uses the same keys as the Aztec Management System>

 

Service	Protocol	Port / Range	Type
Apache	TCP	80	EPOS > Site PC
APOS FTP Control	TCP	20 + 21 Default value can be configured	HO > Site Site > HO HO > external portals
APOS FTP Data	TCP	65000 -> 65019 Default value can be configured	HO > external portals
APOS Ping	ICMP	-	HO > Site Site > HO (any ATP service machine) HO ATP > HO ATP HO ATP > external portals
Audit Reader	TCP	15001 Can be configured	Audit Reader > EPOS Terminals
Aztec CLM Loyalty	TCP	50000	EPOS > Site PC
Aztec CLM Web	TCP	50006	EPOS > Site PC
Aztec Comms	TCP	3524	HO > Site Site > HO
Aztec Distribution Service	TCP	3527	HO > Site Site > HO
Aztec Enhanced Stock Mode	TCP	50005	EPOS < > Site PC
Aztec Import Service (SMTP)	TCP	25	Import Email Service
Aztec Kiosk WCF Terminal	TCP	1471	Kiosk NT Terminal (Zonal) <-> Kiosk Application (Shere)
Aztec Table Management Service	TCP	50001	(loopback)Site PC < > iZoneTablesTerminal
Aztec Table Management Service	TCP	1433	(loopback)Site PC < > iZoneTablesTerminal
Aztec Table Management Service	TCP	7272	Site PC < > EPOS
AztecBOH (WCF)	TCP	50000	EPOS > Site PC
Card Commerce	TCP	8080	Required for access to loyalty API
Comms Remoting	TCP	4657	Comms server IPC mechanism at HO
Datacash ATS	TCP	443	Site PC > Acquirer
Datacopy	TCP	15201	EPOS
EasyEposConfiguration	UDP / BootP	67 (BootP listens on this UDP port)	EPOS and client on Site PC
EFT/ACK (IP auth)	TCP	443 This is only required when connecting via IP to Datacash’s host, other auth methods take place over ISDN and PSTN. Local port variable	Site > Acquirer
EFT/PCCharge	TCP	3525 / 3526	EPOS > Site PC
EQATEC	TCP	443	Site PC > EQATEC server
File and Print Sharing	TCP	139 + 445	Required for comms interaction
File and Print Sharing	UDP	137 + 138	Required for comms interaction
Givex Loyalty	TCP	50019	EPOS > Aztec Web Server
Handheld Bundle	TCP	4000	Site PC > EPOS
Handheld Pickups	TCP	5000	EPOS > Site PC
I700 Update Service	TCP	3528 / 3529	Site PC > I700 platform
Internal Transfers	TCP	1433 Default value can be configured, AS THIS IS THE DEFAULT PORT FOR SQL SERVER, CUSTOMERS ARE STRONGLY ADVISED TO LIMIT ACCESS TO KNOWN IP ADDRESSES ONLY.	Site PC > other Site PC
iServe	TCP	50001	Handheld > Site PC
iServe	UDP	50001	Site PC > Handheld
iServe Config Site Server	TCP	50012
Kitchen iQ Audit Extractor	TCP	27017	-
Kitchen iQ Config Server	TCP	80	-
Kitchen iQ Site Server	TCP	50010
Message Hub Config Server	TCP	81	-
Message Hub Site Server	TCP	50011
MOA Terminals	TCP	15500 - 15755	MOA Terminals > MOA Terminals
Mobile Stocks	HTTP	50001	Site PC < > Handheld
Order Builder	TCP	50015	Site PC < > Customer Cache
Order Builder Application	TCP	50014	Site PC < > Order Builder
POS Integration Engine (formerly iZone)	TCP	Customer Defined This is the port defined in CLM base data settings for the Opera plugin. This is configured per site.	SitePC < > Opera PMS
POS Integration Engine (formerly iZone)	HTTP(S)	443	Site PC < > HLS and PM Pro PMS
POSAnywhere	TCP	10852	Site PC > EPOS
Roaming PED	TCP	20026	PED > Site PC
Sendwce	UDP	463	Site PC > EPOS
Sendwce if using firewall between PC and EPOS	UDP   UDP	Remote 1024 -> Local Ephemeral range Remote 980	EPOS > Site PC   Site PC > EPOS
Site Customer Cache Service	TCP	50008	ZCF Site Proxy > Customer Cache
Site Stocks Service	TCP	50007	ZCF Site Proxy > Site PC (Site Stocks)
Super POS Server	TCP	15203	Server > EPOS
Support / Administration	TCP	1433	Zonal > Sites Zonal > HO
Tables	TCP	80+443+6969 +6970	EPOS / Site PC >Internet based Web Server
Terminal > EPOS Server Comms	TCP	15202	EPOS
US Loyalty	TCP	443	Required for access to loyalty API
ZCPS (ATS Plugin)	TCP	50000	Site PC < > EPOS
ZIPI	TCP	22698 + 22699	EPOS > Site PC
Zoe (till calls)	TCP	>16000+eposIDcalc How to work out the ports required for ZOE Calls to EPoS devices It is only the last byte of the device ID that is added onto the 16000 port number. So far an ID of 1000 (0x3E8) it would be 16000 +0xE8(232) = 16232 How to work out the ports required for ZOE Calls to EPoS devices. A simple way to work it out would be by using the programmer function on the Calculator on your pc and doing the following: EPOS ID = 1000 1. Make sure Dec function is selected 2. Enter in ‘1000’ (EPOS id) 3. Press the ‘Mod’ button 4. Enter in ‘256’ 5. Press enter 6. Answer will be 232 for this example 7. Add 16000 to 232 to get your port number = 16232	Site PC > EPOS
Zonal Connect	HTTP(S)	443	Zonal Connect > HO Proxy
Zonal Connect	HTTP(S)	Customer Defined	Site PC > HO Proxy
Zonal Data Transformation Service (ZDTS)	HTTP	50512	ZDTS Website > ZDTS Service API

 

Application	Web URL	IP Address
Zonal Connect	*.zonalconnect.com	109.233.117.104
Reporting	reporting.zonal.co.uk	109.233.117.104
Freshnet	*.freshnet.co.uk	109.233.117.105
iZone	*.izone-app.com	109.233.117.108
Aztec Table Management Service	https://tables.izone-app.com/	109.233.117.108
Zonal Connect Framework Gateway	All Data Centre outgoing traffic	109.233.117.100

 

* being a wild-card representing anything or nothing